Remove monitor-net from prometheus.tmpl #136
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As per https://stackoverflow.com/questions/66676204/prometheus-node-exporter-in-docker-host-networking-vs-hostnames/66689508#66689508 a hard-coded bridge network is not necessary when using
host.docker.internal:host-gateway
Removing it allows the use of the Grafana stack in environments where other Docker stacks also run, and the hard-coded monitor-net may "step on" existing bridge networks.